Reimplement Workflow with its own schema#1897
Merged
labkey-susanh merged 38 commits intodevelopfrom Dec 1, 2025
Merged
Conversation
…ow-downloadAttachments
XingY
approved these changes
Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
Having our workflow implementation based on the Exp schema leads to lots of inefficiencies and makes it difficult to expand the capabilities. This set of PRs moves the data into dedicated tables in the database, producing a new rendition of the
workflowschema.Related Pull Requests
Changes
WORKFLOWschema and queries and remove legacy job schema/query references